-
Notifications
You must be signed in to change notification settings - Fork 5
Fix CI Suite, support circleci stanza, other fixes #45
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
Conversation
Support new CircleCI stanza for Catalog Entities
Pull in upstream changes
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.
Thanks for the PR! I'll look into getting the token updated in this repo so CI passes again.
@@ -53,7 +53,6 @@ resource %[1]q %[2]q { | |||
] | |||
} | |||
filter = { | |||
category = "SERVICE" |
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.
Thanks for removing this. I can file an internal bug to get the provider updated to support include/exclude types (which is what replaced category).
@splittingred I opened #47 to figure out how we are gonna tackle the CI issues here. I'm leaning towards just merging your PR and then fixing it up on our side with changes so that the acceptance tests only run on the main branch. Feel free to comment on that issue if you've got feedback on either approach. I'm also running this by our internal team. |
This was addressed in #45 but regressed in #46 after changes to the acceptance testing flow. Category is deprecated in the Cortex API and the provider will need an update to adopt the newer filtering approach. In the meantime, we just remove the feature from acceptance testing and mark it as deprecated.
Does the following:
x-cortex-circle-ci
in catalog entitiestenv
linter which is deprecatedfilter.category
(which doesnt exist anymore in Cortex API - fixing this in TF provider will need seperate work)I am assuming the CI suite wont pass because I'm not granted GH secrets access to
CORTEX_API_TOKEN
. You can see these changes working in our fork (which uses the same Cortex workspace for the CI suite), anyway: https://github.com/bigcommerce/terraform-provider-cortex/actions/runs/13866159540/job/38805627263