Skip to content
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

Container Cluster fixes #1794

Closed
wants to merge 5 commits into from
Closed

Container Cluster fixes #1794

wants to merge 5 commits into from

Conversation

rambleraptor
Copy link
Contributor

Addressing ansible/ansible#56426

  • initialClusterVersion is not output-only
  • Need support for resourceLabels

[all]

[terraform]

[terraform-beta]

[ansible]

[inspec]

@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician, I work on Magic Modules.
This PR seems not to have generated downstream PRs before, as of 261530aeebbcffc77b6c6affde02ddd7e753843c.

Pull request statuses

No diff detected in terraform-provider-google-beta.
No diff detected in terraform-google-conversion.
No diff detected in terraform-provider-google.

New Pull Requests

I built this PR into one or more new PRs on other repositories, and when those are closed, this PR will also be merged and closed.
depends: modular-magician/ansible#249
depends: modular-magician/inspec-gcp#157

@rambleraptor
Copy link
Contributor Author

@slevenick This InSpec PR violates the InSpec repo's Rubocop rules. I turned off Rubocop runs during code-generation because I don't think they belong there.

@rambleraptor
Copy link
Contributor Author

@slevenick - InSpec + Rubocop removal
@SirGitsalot - normal code review

@@ -15,10 +15,6 @@ do
bundle exec compiler -p $i -e inspec -o "build/inspec/"
done

pushd build/inspec
rubocop -c .rubocop.yml
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why are we removing this?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed it in this PR because it was giving errors that was blocking generation (CyclomaticComplexity was too high in generated code).

More broadly, since we're not using this for auto-correction in this step, it seems like it should be moved into inspec-unit-test so it doesn't block generation.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah cyclomatic complexity strikes again. Ok I can add it to the unit test step and modify that rubocop file

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you turn off those kinds of rules (CyclomaticComplexity, AbcSize, etc). I don't think they add any value.

The GKE API makes it look like updating initialClusterVersion is the
proper way of specifying the Kubernetes API version.
@modular-magician
Copy link
Collaborator

Hi! I'm the modular magician, I work on Magic Modules.
I see that this PR has already had some downstream PRs generated. Any open downstreams are already updated to your most recent commit, 50372d5.

Pull request statuses

No diff detected in terraform-google-conversion.
Ansible already has an open PR.
InSpec already has an open PR.

New Pull Requests

I built this PR into one or more new PRs on other repositories, and when those are closed, this PR will also be merged and closed.
depends: hashicorp/terraform-provider-google-beta#766
depends: hashicorp/terraform-provider-google#3712

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants