Skip to content
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update deprecation warning to tombstone entry
  • Loading branch information
beeankha committed Apr 21, 2025
commit c9c1471fc59e8affb8f7bb65194252edb0db863b
2 changes: 1 addition & 1 deletion meta/runtime.yml
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ plugin_routing:
openshift:
redirect: community.okd.openshift
k8s:
deprecation:
tombstone:
removal_version: 6.0.0
warning_text: >-
The k8s inventory plugin has been deprecated and
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 am getting the following sanity test error:

ERROR: Found 1 runtime-metadata issue(s) which need to be resolved:
ERROR: meta/runtime.yml:0:0: The tombstone removal_version ('6.0.0') must not be after the current version for dictionary value @ data['plugin_routing']['inventory']['k8s']['tombstone']['removal_version']. Got '6.0.0'

Do we need to wait until after 6.0.0 is release before we change deprecation: to tombstone:?

Copy link
Contributor

@yurnov yurnov Apr 21, 2025

Choose a reason for hiding this comment

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

To have it passed, you need to put a version like 6.0.0-dev0 in the galaxy.yaml as I did in the #867

Ideally, to complete ACA-2407 and as the preparation to ACA-2406 I recommend following:

/att @gravesm as the reporter of ACA-2407 and one of repo maintainer.

ps: I can help with the #867 and associated CI issues, if any, You can see that I have some contributions over the last year

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@yurnov thanks so much for listing this all out. The two github_actions PRs have been merged; there is a merge conflict in #867, please let me know if you need any help with it.

Once we get the conflict sorted out and the CI re-run, we can take another look at that PR.

Expand Down
Loading