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
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
As an operator, I don't want to import a particular Fabrikate definition and then have an unrelated change in another definition trigger a CI/CD build that pulls in a new version of this definition.
Instead, we should version lock definitions such that if a downstream user specifies a specific git commit as a version that the resource manifests it generates are always the same.
The text was updated successfully, but these errors were encountered:
As an operator, I don't want to import a particular Fabrikate definition and then have an unrelated change in another definition trigger a CI/CD build that pulls in a new version of this definition.
Instead, we should version lock definitions such that if a downstream user specifies a specific git commit as a
version
that the resource manifests it generates are always the same.The text was updated successfully, but these errors were encountered: