Skip to content

Conversation

@antromeo
Copy link
Contributor

No description provided.

@github-actions
Copy link

Requested publication of version 1.1.0-ENG-4951-PR-174

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix the "coverage" issues

@antromeo
Copy link
Contributor Author

Wait ENG-4950

@antromeo antromeo requested a review from avdev4j June 21, 2023 07:23
@avdev4j
Copy link
Contributor

avdev4j commented Jun 23, 2023

Is the svc files supposed to be in the bundle? Because there only present in the src project that not always contains the bundle descriptors. So, I was thinking we focus on the delivered v1 bundle that doesn't contain the svc, for sure

@antromeo antromeo marked this pull request as ready for review June 26, 2023 07:15
@antromeo
Copy link
Contributor Author

Is the svc files supposed to be in the bundle? Because there only present in the src project that not always contains the bundle descriptors. So, I was thinking we focus on the delivered v1 bundle that doesn't contain the svc, for sure

In Bundle URI, you probably won't find them, but that's an optional step where the svc path folder is a user input and the user can specify the path if they are used locally wherever they are.
In next steps, if we choose to support Source URL, this optional step will become more useful than now.

CC: @firegloves

@antromeo antromeo closed this Jun 26, 2023
@antromeo antromeo reopened this Jun 26, 2023
@github-actions
Copy link

Requested publication of version 1.1.0-ENG-4951-PR-174

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix the "coverage" issues

@avdev4j
Copy link
Contributor

avdev4j commented Jun 26, 2023

@antromeo thanks for the further information. It makes sense now, I would suggest making the prompt more obvious (maybe give more details in the prompt sentence). As you said, if we also support the sources Bundle, it will be more useful because we are almost sure to have them.

Another solution would be to ask the user if he/she wants to add the svc and then ask for the path.

@antromeo
Copy link
Contributor Author

@avdev4j in my opinion two questions are maybe too verbose.
Yes the sentence could be improved in something like "Enter the svc path if you are using svc files".
Let me know for your suggestions


// adds services
servicePath = servicePath ?? await CliUx.ux.prompt(
'Services path (optional)',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
'Services path (optional)',
'Please provide the path to the service files source code (optional)',

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion from @jyunmitch

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@avdev4j, @jyunmitch
just a note: what do you think if we took away the words "source code"? because docker compose files are actually yaml files (no source)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this work? "Please provide the path to the YAML service files (optional)"
or "Please provide the path to the Docker Compose service files (optional)"

@antromeo antromeo requested a review from avdev4j June 27, 2023 13:09
@github-actions
Copy link

Requested publication of version 1.1.0-ENG-4951-PR-174

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please fix the "coverage" issues

@antromeo antromeo merged commit acb9d5c into develop Jun 27, 2023
@github-actions
Copy link

Requested publication of version 1.1.0-ENG-4951-PR-174

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants