[
https://issues.apache.org/jira/browse/AMBARI-24809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16660764#comment-16660764
]
Paulo Moraes Moura edited comment on AMBARI-24809 at 10/23/18 2:51 PM:
-----------------------------------------------------------------------
Just discovered that the repo customization should be done throught the version
definition since Ambari 2.6.
https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.0.0/bk_ambari-release-notes/content/ambari_relnotes-2.6.0.0-behavioral-changes.html
Maybe displaying a deprecated warning to any calls made to the old api would be
helpful.
was (Author: pmoraesm):
Just discovered that the repo customization should be done throught the version
definition since Ambari 2.6.
Maybe displaying a deprecated warning to any calls made to the old api would be
helpful.
> API Call to change the repository configuration doesn't work
> ------------------------------------------------------------
>
> Key: AMBARI-24809
> URL: https://issues.apache.org/jira/browse/AMBARI-24809
> Project: Ambari
> Issue Type: Bug
> Components: ambari-sever
> Affects Versions: 2.7.1
> Reporter: Paulo Moraes Moura
> Priority: Major
> Attachments: ambari-audit.log, curl_get_new_repo.txt,
> curl_put_new_repo.txt, hdp-3.0-repo.json
>
>
> Updating the repository configuration through the API call isn't working.
> After submitting the request, a status 200 is received and an update repo
> configuration line is printed in the ambari-audit.log, but the public repo
> still is used in the installation.
>
> Attached:
> * curl PUT request to update repo configuration
> * json file containing desired configuration
> * ambari-audit.log showing the update
> * curl GET request to retrieve the values after performing the PUT
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
