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

[RFE] Enable/Disable automate domains #649

Open
ThomasBuchinger opened this issue Aug 13, 2019 · 11 comments
Open

[RFE] Enable/Disable automate domains #649

ThomasBuchinger opened this issue Aug 13, 2019 · 11 comments

Comments

@ThomasBuchinger
Copy link

ThomasBuchinger commented Aug 13, 2019

ManageIQ recently implemented the create_from_git action on /api/automate_domains. By default the new domain is set to disabled. This is by design, because there should be an administrator "approving" the domain, by enabling it manually.

However CI/CD pipelines need to enable the new domains automatically.
My particular use case involves generating Automate Domains on the fly, based on pull requests in git. These Domains are pushed to the central git repo as orphaned branch, a call to create_from_git that imports the domain, before the orphaned branch is cleaned up.

A separate action to set the enabled field in MiqAeDomain would solve that problem

Original RFE: #354
PR: #571
My Project: ThomasBuchinger/miq-flow#52
Gitter conversation:

@Fryguy
Copy link
Member

Fryguy commented Aug 13, 2019

As discussed, in my opinion this should already be possible since it's an attribute and attributes can be modified via PUT/PATCH

@abellotti
Copy link
Member

if exposed yes, but it is not today. The API needs to be enhanced to support /api/automate_domains updates (post edit action or patch).

From miq_product_features.yml, looks like the user entitlement to be associated with this action would be "miq_ae_domain_edit", so essentially adding:

:post:
- :name: edit
   :identifier: miq_ae_domain_edit

in collection & resource actions for automate_domains.

base controller's update methods should handle this fine unless some other checks are needed in the api controller, should be minor.

/cc @mkanoor

@ThomasBuchinger
Copy link
Author

ThomasBuchinger commented Aug 16, 2019

I did some testing on my Ivanchuck appliance today. And just adding @abellotti snippet to config/api.yml does work for me

POST /api/automate_domains/169
{
    "action": "edit"
    "resource": {
        "enabled": true
    }
}

In theory you could already patch any attribute over API as it is today:

PATCH /api/automate_domains/169
{
    "enabled": true
}

@abellotti
Copy link
Member

PR resolving this issue by @skateman: #647

@ThomasBuchinger
Copy link
Author

You guys are faster with the implementation, than I am with setting up my development environment
Anyway is there anything I can do to get that feature into Ivanchuk down the line? Probably it is best to talk to RedHat support?

Second, I think nobody is currently working on an update to the API reference? I am going to open a PR

@ThomasBuchinger
Copy link
Author

@abellotti ^

@miq-bot miq-bot added the stale label Feb 24, 2020
@miq-bot
Copy link
Member

miq-bot commented Feb 24, 2020

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

@mfeifer
Copy link
Contributor

mfeifer commented Mar 6, 2020

@abellotti has this been addressed? can it be closed?

@abellotti
Copy link
Member

Not yet, discussions are pending with the related PR #647 so let's keep this open.

@miq-bot
Copy link
Member

miq-bot commented Feb 27, 2023

This issue has been automatically marked as stale because it has not been updated for at least 3 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

@miq-bot miq-bot added the stale label Feb 27, 2023
@miq-bot
Copy link
Member

miq-bot commented May 29, 2023

This issue has been automatically closed because it has not been updated for at least 3 months.

Feel free to reopen this issue if this issue is still valid.

Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.

@Fryguy Fryguy moved this to Backlog in Roadmap Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

7 participants