You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only bridged providers benefit from the consistency and automatic rollout of workflows generated from provider-ci today. This creates a lot of work when we have to make a change to all providers. Native provider ci also helps automate changes for some non-bridged providers but has also varied in structure to provider-ci. We'd like to drive greater consistency for across the whole fleet for things like package publish to gain the benefits of investment here across the whole fleet.
Key KPIs
Number of implementations required to roll out a publishing change to all providers.
Number of duplicate implementations where behaviour is the same.
Key Stakeholders
Provider team
Community provider authors
Key Deliverables
New provider-ci templates for EKS, AWSx and API Gateway
Why does the title say Standardize on CI-mgmt for all providers and the overview says "Bridged providers currently display unusable or misleading results in pulumi preview." ?
Overview
Only bridged providers benefit from the consistency and automatic rollout of workflows generated from provider-ci today. This creates a lot of work when we have to make a change to all providers. Native provider ci also helps automate changes for some non-bridged providers but has also varied in structure to provider-ci. We'd like to drive greater consistency for across the whole fleet for things like package publish to gain the benefits of investment here across the whole fleet.
Key KPIs
Key Stakeholders
Key Deliverables
References 📔
The text was updated successfully, but these errors were encountered: