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.

Sign up for GitHub

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

Jump to bottom

Add an Ansible Stack #11877

Closed
slemeur opened this issue Nov 8, 2018 · 14 comments
Closed

Add an Ansible Stack #11877

slemeur opened this issue Nov 8, 2018 · 14 comments
Labels
area/devfile-registry kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@slemeur
Copy link
Contributor

slemeur commented Nov 8, 2018

Description

Ansible Stack with YAML, Ansible-Review, Ansible-Lint
@slemeur slemeur added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Nov 8, 2018
@victorock
Copy link

@slemeur Any updates on this?

@slemeur
Copy link
Contributor Author

slemeur commented Mar 12, 2019

That is not something we have prioritized right now. (Probably post Che 7 GA)

With Che 7, the stacks are revisisted and getting much simpler to create. If you have a container with ansible-review and ansible-lint integrated, it's completely possible create a stack which will provide those tools + the appropriated language server.

We are writing documentation on how to create those new Che 7 stacks, but if you are interested, it is something we can explore together.

@victorock
Copy link

Absolutely @slemeur, just let me know how i can help.
I already have a "ansible developper" container image.

@l0rd l0rd mentioned this issue Mar 20, 2019
Closed
77 tasks
@slemeur
Copy link
Contributor Author

slemeur commented Mar 20, 2019

Wonderful.
I added that into the scope of Che 7 GA - I think it would be very interesting if you can contribute that with some help from @tsmaeder 's team.

Creating a devfile would be the initial way to move forward: https://redhat-developer.github.io/devfile/
We are still working on the documentation, but feel free to ping @mshaposhnik or @sleshchenko.

@victorock
Copy link

victorock commented Aug 13, 2019 •
edited
Loading

i have a container for it, using default theia-runtime (i'd prefer to use UBI).
I am doing some tests now, so i may have the container with the remote-plugin and requirements for ansible ready by end of this week. Next i'll investigate about the proper devfile.

@slemeur
Copy link
Contributor Author

slemeur commented Aug 13, 2019

Sounds good @victorock ! In this case, I'll add the label 7.1.0, as it seems you would be able to provide a PR after 7.0.0 release.
Would be ideal to add the stack to the default stacks (devfile registry: https://github.com/eclipse/che-devfile-registry)

@slemeur slemeur added this to the 7.0.0 milestone Aug 13, 2019
@slemeur slemeur added area/devfile area/devfile-registry kind/enhancement A feature request - must adhere to the feature request template. and removed area/devfile kind/task Internal things, technical debt, and to-do tasks to be performed. labels Aug 13, 2019
@slemeur slemeur modified the milestones: 7.0.0, 7.1.0 Aug 13, 2019
@sunix
Copy link
Contributor

sunix commented Aug 15, 2019

We have a draft plugin + devfile here: https://github.com/sunix/che-ansible

@che-bot
Copy link
Contributor

che-bot commented Feb 12, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 12, 2020
@che-bot che-bot closed this as completed Feb 19, 2020
@sympatheticmoose sympatheticmoose removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 13, 2021
@sympatheticmoose
Copy link

Additionally for consideration is the new Ansible extension for VS Code

benoitf added a commit to benoitf/che-plugin-registry that referenced this issue May 19, 2021
@benoitf
feat(ansible): Add a sidecar with Ansible tooling installed inside
3a8e367 
related to eclipse-che/che#11877

Change-Id: Ifc1af877a797fd1b0043ed3574a5adac0e204e1d
Signed-off-by: Florent Benoit <fbenoit@redhat.com>
@benoitf benoitf mentioned this issue May 19, 2021
Merged
9 tasks
ericwill pushed a commit to eclipse-che/che-plugin-registry that referenced this issue May 19, 2021
@benoitf
feat(ansible): Add a sidecar with Ansible tooling installed inside (#961
252f988 
)

related to eclipse-che/che#11877

Change-Id: Ifc1af877a797fd1b0043ed3574a5adac0e204e1d
Signed-off-by: Florent Benoit <fbenoit@redhat.com>
@che-bot
Copy link
Contributor

che-bot commented Nov 22, 2021

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 22, 2021
@svor
Copy link
Contributor

svor commented Nov 22, 2021

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 22, 2021
@che-bot
Copy link
Contributor

che-bot commented May 21, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 21, 2022
@svor svor removed this from the 7.1.0 milestone May 23, 2022
@svor
Copy link
Contributor

svor commented May 23, 2022

/remove-lifecycle stale

@che-bot che-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 23, 2022
@che-bot
Copy link
Contributor

che-bot commented Nov 19, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 19, 2022
@che-bot che-bot closed this as completed Nov 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/devfile-registry kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@sunix @svor @slemeur @victorock @sympatheticmoose @che-bot