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

[WIP] Added basic PostStart functionality #3283

Closed

Conversation

upLukeWeston
Copy link
Contributor

What type of PR is this?
/kind feature

What does does this PR do / why we need it:
Adds the basic functionality for PostStart commands to be executed when a container is first created.

Which issue(s) this PR fixes:
Fixes #2936

How to test changes / Special notes to the reviewer:
Blocked by #3216

Aditi Sharma and others added 23 commits June 2, 2020 13:06
* Add Devfile Parser for Version 2.0.0

Added Devfile V2 Go Structures
Added converter for v2 ro common types

Signed-off-by: adisky <adsharma@redhat.com>

* Add example V2 devfile

added example nodejs V2 devfile

* Add Common Types as V2

Add common types as v2
Add Converter from common to v1

* Updated example devfile with group
Signed-off-by: mik-dass <mrinald7@gmail.com>
Signed-off-by: mik-dass <mrinald7@gmail.com>
…3206)

* Update Docker and Kubernetes adapter to use groups

* Update Some Validation

Incorporate some review comments for commands Map
Update Some Validation logic
Fixed interface implementation for v2
Updated logs
refactored commands.go
While converting v1 to v2 types, string pointers are prone to cause
null pointer error. This PR updates struct fields from string
pointers to string
* Update command tests

Updated Command tests to v2
Removed some cases like command type validation, that will be
validated by schema only.

* Fix common adapters tests

All devfile.adapters.common unit tests are fixed

* Add tests for Mismatched type

Fix devfile.adapters.Kubernetes.Component unit tests

* Add TestCase for default command
… status for IDE integration for devfile scenarios (redhat-developer#2550) (redhat-developer#3177)

* Add event notification proposal

[skip ci]

* Update event-notification.md

* Update event-notification.md

* Update event-notification.md

* Update event-notification.md

* Update event-notification.md

* Update event-notification.md

* Update event-notification.md

* Update event-notification.md
* Fix Integration tests

Correct volume structure
Fix supervisord binary insertion for docker
Insert command and args in build container fr docker

* Fix Integration tests

Revert commands, args removal
Add commands, args in v2 common structs
Fix duplicate volume error
Signed-off-by: mik-dass <mrinald7@gmail.com>
Add devfiles v2 examples for springboot and nodejs
fix regression caused by rebase to master.
Also add github, zip as supported project types.
fix log levels to v4
fix error formatting
add case no's in test cases
update some comments
Remove validation for group
@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. Required by Prow. kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation labels Jun 2, 2020
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign dharmit
You can assign the PR to them by writing /assign @dharmit in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci-robot openshift-ci-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. Required by Prow. label Jun 2, 2020
@openshift-ci-robot
Copy link
Collaborator

Hi @upLukeWeston. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@kadel
Copy link
Member

kadel commented Jun 3, 2020

I'm afraid that it is too early for this PR.
See #2936 (comment), I don't want to fragment the discussion

@upLukeWeston
Copy link
Contributor Author

Sure, no problem! I'll close this PR then and we can continue the discussion on the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. Required by Prow. kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. Required by Prow.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Container initiailization support
5 participants