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

Remove unused project mentions #12188

Merged
merged 2 commits into from
Oct 22, 2024
Merged

Conversation

akiioto
Copy link
Contributor

@akiioto akiioto commented Oct 22, 2024

Description

Changes proposed in this pull request:

  • Remove occurencies of "sap-kyma-prow-workloads" in configs
  • ...
  • ...

Related issue(s)

#9771

@akiioto akiioto requested review from neighbors-dev-bot and a team as code owners October 22, 2024 11:30
@kyma-bot kyma-bot added cla: yes Indicates the PR's author has signed the CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 22, 2024
@kyma-bot
Copy link
Contributor

kyma-bot commented Oct 22, 2024

❌ Plan Result

CI link

Error: Provider configuration not present

To work with
google_project_iam_member.service_account_keys_cleaner_workloads_project
(orphan) its original provider configuration at
provider["registry.opentofu.org/hashicorp/google"].workloads is required, but
it has been removed. This occurs when a provider configuration is removed
while objects created by that provider still exist in the state. Re-add the
provider configuration to destroy
google_project_iam_member.service_account_keys_cleaner_workloads_project
(orphan), after which you can remove the provider configuration again.

Error: Provider configuration not present

To work with
google_project_iam_member.service_account_keys_rotator_workloads_project
(orphan) its original provider configuration at
provider["registry.opentofu.org/hashicorp/google"].workloads is required, but
it has been removed. This occurs when a provider configuration is removed
while objects created by that provider still exist in the state. Re-add the
provider configuration to destroy
google_project_iam_member.service_account_keys_rotator_workloads_project
(orphan), after which you can remove the provider configuration again.

@akiioto akiioto closed this Oct 22, 2024
@akiioto akiioto reopened this Oct 22, 2024
@akiioto akiioto closed this Oct 22, 2024
@akiioto akiioto reopened this Oct 22, 2024
@akiioto
Copy link
Contributor Author

akiioto commented Oct 22, 2024

/override pull-plan-prod-terraform

@kyma-bot
Copy link
Contributor

@akiioto: akiioto unauthorized: /override is restricted to Repo administrators.

In response to this:

/override pull-plan-prod-terraform

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@Sawthis
Copy link
Contributor

Sawthis commented Oct 22, 2024

/override pull-plan-prod-terraform

@kyma-bot
Copy link
Contributor

@Sawthis: /override requires failed status contexts, check run or a prowjob name to operate on.
The following unknown contexts/checkruns were given:

  • pull-plan-prod-terraform

Only the following failed contexts/checkruns were expected:

  • license/cla
  • tide

If you are trying to override a checkrun that has a space in it, you must put a double quote on the context.

In response to this:

/override pull-plan-prod-terraform

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kyma-bot kyma-bot added the lgtm Looks good to me! label Oct 22, 2024
@kyma-bot kyma-bot merged commit 0ba5f3b into kyma-project:main Oct 22, 2024
146 checks passed
@kyma-bot
Copy link
Contributor

@akiioto: Updated the following 2 configmaps:

  • job-config configmap in namespace default at cluster default using the following files:
    • key periodics.yaml using file prow/jobs/kyma-project/test-infra/periodics.yaml
  • config configmap in namespace default at cluster default using the following files:
    • key config.yaml using file prow/config.yaml

In response to this:

Description

Changes proposed in this pull request:

  • Remove occurencies of "sap-kyma-prow-workloads" in configs
  • ...
  • ...

Related issue(s)

#9771

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kyma-bot
Copy link
Contributor

❌ Apply Result

CI link

Error: Provider configuration not present

To work with
google_project_iam_member.service_account_keys_rotator_workloads_project
(orphan) its original provider configuration at
provider["registry.opentofu.org/hashicorp/google"].workloads is required, but
it has been removed. This occurs when a provider configuration is removed
while objects created by that provider still exist in the state. Re-add the
provider configuration to destroy
google_project_iam_member.service_account_keys_rotator_workloads_project
(orphan), after which you can remove the provider configuration again.

Error: Provider configuration not present

To work with
google_project_iam_member.service_account_keys_cleaner_workloads_project
(orphan) its original provider configuration at
provider["registry.opentofu.org/hashicorp/google"].workloads is required, but
it has been removed. This occurs when a provider configuration is removed
while objects created by that provider still exist in the state. Re-add the
provider configuration to destroy
google_project_iam_member.service_account_keys_cleaner_workloads_project
(orphan), after which you can remove the provider configuration again.
Details (Click me)
Acquiring state lock. This may take a few moments...

Error: Provider configuration not present

To work with
google_project_iam_member.service_account_keys_rotator_workloads_project
(orphan) its original provider configuration at
provider["registry.opentofu.org/hashicorp/google"].workloads is required, but
it has been removed. This occurs when a provider configuration is removed
while objects created by that provider still exist in the state. Re-add the
provider configuration to destroy
google_project_iam_member.service_account_keys_rotator_workloads_project
(orphan), after which you can remove the provider configuration again.

Error: Provider configuration not present

To work with
google_project_iam_member.service_account_keys_cleaner_workloads_project
(orphan) its original provider configuration at
provider["registry.opentofu.org/hashicorp/google"].workloads is required, but
it has been removed. This occurs when a provider configuration is removed
while objects created by that provider still exist in the state. Re-add the
provider configuration to destroy
google_project_iam_member.service_account_keys_cleaner_workloads_project
(orphan), after which you can remove the provider configuration again.

`

@Sawthis Sawthis assigned akiioto and unassigned Sawthis Oct 31, 2024
KacperMalachowski pushed a commit to KacperMalachowski/test-infra that referenced this pull request Nov 6, 2024
* Remove unused project mentions

* Remove unused project mentions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Indicates the PR's author has signed the CLA. lgtm Looks good to me! size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants