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
It would be nice to see the releases with the respective atmos version. The releases are generally patch releases and most people do not pin their releases to a specific version but pin to the latest patch release. Sometimes a newer patch release comes out and breaks terraform runs because the local atmos also needs to be updated.
Expected Behavior
If the atmos version is included with the utils provider, it would be less hunting to find the associated atmos release associated. Sometimes these new releases do not include an atmos release update so it would be fine for those releases to use the current atmos version associated.
Then if something breaks, we can ensure the provider release and atmos release are aligned, before submitting an issue.
e.g. provider version 0.17.23 points to atmos version 1.4.11 so they should be used together to eliminate a version difference.
The text was updated successfully, but these errors were encountered:
Have a question? Please checkout our Slack Community or visit our Slack Archive.
Describe the Feature
It would be nice to see the releases with the respective atmos version. The releases are generally patch releases and most people do not pin their releases to a specific version but pin to the latest patch release. Sometimes a newer patch release comes out and breaks terraform runs because the local atmos also needs to be updated.
Expected Behavior
If the atmos version is included with the utils provider, it would be less hunting to find the associated atmos release associated. Sometimes these new releases do not include an atmos release update so it would be fine for those releases to use the current atmos version associated.
Then if something breaks, we can ensure the provider release and atmos release are aligned, before submitting an issue.
e.g. provider version 0.17.23 points to atmos version 1.4.11 so they should be used together to eliminate a version difference.
The text was updated successfully, but these errors were encountered: