-
Notifications
You must be signed in to change notification settings - Fork 636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FLPROD-1439: Make terraform config consistent with the API on declaring optional fields for snippet rules #4787
FLPROD-1439: Make terraform config consistent with the API on declaring optional fields for snippet rules #4787
Conversation
changelog detected ✅ |
Optional: true, | ||
Optional: true, | ||
PlanModifiers: []planmodifier.String{ | ||
defaults.DefaultString(""), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we need an empty string here? or can it be totally optional?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed this, used the same planmodifier rulesets are using for description field (we need the same behaviour as in ordinary rulesets)
Marking this pull request as stale due to 14 days of inactivity. This helps our maintainers find and focus on the active pull requests. If this pull request receives no comments in the next 7 days it will automatically be closed. Maintainers can also remove the |
Marking this pull request as stale due to 14 days of inactivity. This helps our maintainers find and focus on the active pull requests. If this pull request receives no comments in the next 7 days it will automatically be closed. Maintainers can also remove the |
…ng optional fields for snippet rules and use list block for rules based products
382c70f
to
a4a4a4a
Compare
looks like snippet_rules are failing acceptance tests
|
Hm, this is probably api failure on our side inside the service (I see some timeouts during the day on db queries inside the service). Just run the test multiple times: |
found the issue and now this is all good
|
No description provided.