This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Thank you for your feedback. We will pass this to our development team this week for further review. I am placing this in the 'Under Review' state.
Step 1 can become complicated overtime :-
1. if we need to make any changes in the Generic process to fix any issues , then every time that has cloned the process will have to make changes.
Also the token will have to be updated in the Udeploy properties (using another cron job from an externally) every 60 minutes
With the future maintenance and ease of use of a Plugin in as mentioned in Option 2 will be the best option
Our team reviewed this request and we have two options to offer to you for your feedback:
These are two options our team can see for Idea DVOPS-I-841:
Create a generic process that uses input properties to perform the “Clone from GitHub App” which can be used generically by all teams. Essentially your process would call this Generic Process to do the clone. If you already have a shell step that is doing this today, you could use this in the Generic Process. Your component process can call the ‘Run Generic Process’ step to perform the clone.
This may save you time as you don’t have to wait on our team to create a plugin. You may be able to do this on your own without our help.
We could conceivably create an “automation plugin” that would use the plugin step to perform the Git Clone. We think it would be a two-step process. First, using the JWT token you provide our plugin step, we call GitHub to get the access token. Second, we would use the access token to clone the GitHub repository. The team spoke about how we could have secrets (the JWT token) stored in Deploy and then we would use our Vault property resolution feature already in the system to resolve that property.
Regardless of option 1 or 2, we think each GitHub App would have a unique secret as they will differ between repositories.
If we create the GitHub automation plugin, you could then have your component process call this automation plugin step directly in your process without using the Generic Process mechanism.
Please let us know which approach you feel would be the best to meet your needs. Thank you.
Thank you for this additional information. We will take this back to the development team soon.
User's need to clone repositories from GitHub.com so that they can execute Ansible Playbooks or any bash scripts in their deployment processes .
In order to clone using GitHub App , as per documentation https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/generating-a-json-web-token-jwt-for-a-github-app they need to first generate a JST or https://docs.github.com/en/apps/creating-github-apps/authenticating-with-a-github-app/generating-a-user-access-token-for-a-github-app user access Token which is short lived
And then clone this GitHub repo using that token
This requires writing additional script every time a repo needs to be cloned by all teams
If this step can be accomplished using a plugin , it will make it easier for developments teams to use Udeploy
Similar plugin https://www.jenkins.io/blog/2020/04/16/github-app-authentication/ is being used in Jenkins
Thank you for submitting this idea. Could you please clarify what you are wanting to help you clone the GitHub repository in your Udeploy processes? We are not clear on what you are asking for. We met yesterday and the development team needs this additional information.
I will move this to the 'Needs more information' state as we await your response.
Thank you very much for submitting this idea. We have created a discussion topic to review the idea with our development team this week. I am moving the idea to the 'Under Review' state. We will be in touch.