Skip to content

fix!: Name field in config does not affect path anymore #265

Closed
amanenk wants to merge 16 commits intocloudquery:mainfrom
amanenk:fix/name_detach_from_path
Closed

fix!: Name field in config does not affect path anymore #265
amanenk wants to merge 16 commits intocloudquery:mainfrom
amanenk:fix/name_detach_from_path

Conversation

@amanenk
Copy link
Copy Markdown
Contributor

@amanenk amanenk commented Oct 7, 2022

Summary

closes #256

Also fixed a bug with multi config files on windows.


Use the following steps to ensure your PR is ready to be reviewed

  • Read the contribution guidelines 🧑‍🎓
  • Run go fmt to format your code 🖊
  • Lint your changes via golangci-lint run 🚨 (install golangci-lint here)
  • Update or add tests 🧪
  • Ensure the status checks below are successful ✅

@github-actions github-actions bot added the fix label Oct 7, 2022
@amanenk amanenk marked this pull request as ready for review October 7, 2022 17:21
@amanenk amanenk requested a review from yevgenypats as a code owner October 7, 2022 17:21
@yevgenypats yevgenypats changed the title fix: Name field in config does not affect path anymore fix!: Name field in config does not affect path anymore Oct 9, 2022
@github-actions github-actions bot added breaking and removed fix labels Oct 9, 2022
Copy link
Copy Markdown
Contributor

@yevgenypats yevgenypats left a comment

Choose a reason for hiding this comment

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

Nice catch with the windows bug!

I like that. we just need to update the documentation and also I made it a breaking change.
Agree this will make it less confusing on the connection of name and path as name will be just required alias and path required path of the plugin.

Will let @hermanschaaf take a look as well.

Copy link
Copy Markdown
Contributor

@hermanschaaf hermanschaaf left a comment

Choose a reason for hiding this comment

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

Great fixes. I suggested a few small changes.

For releasing this: we should mark this SDK change as breaking (already done), but we should also remember that the CLI update will be breaking. If we are thinking about any other backwards-incompatible config changes, we should bundle them in that release too. (Here I'm thinking about the two spec config entries confusing some users)

yevgenypats and others added 3 commits October 10, 2022 14:04
Co-authored-by: Herman Schaaf <hermanschaaf@gmail.com>
Co-authored-by: Herman Schaaf <hermanschaaf@gmail.com>
Co-authored-by: Herman Schaaf <hermanschaaf@gmail.com>
@hermanschaaf
Copy link
Copy Markdown
Contributor

After some discussion, we decided to hold back on this change so as to not force a breaking change so soon after the release of v1. But in the meantime we should start updating documentation to always include an explicit path and clearly indicate that name can be anything.

When we have a few more breaking changes to make, we will bundle it together in a new release.

@hermanschaaf hermanschaaf marked this pull request as draft October 10, 2022 13:39
@hermanschaaf
Copy link
Copy Markdown
Contributor

hermanschaaf commented Nov 7, 2022

Closed by #368 and #352

kodiakhq bot pushed a commit that referenced this pull request Nov 8, 2022
This updates (and replaces) this earlier PR for making `path` a required config parameter: #265

We have received numerous user reports of the distinction between name and path being confusing, so rather than infer path from name in some circumstances (and not in some others), this change makes things consistent by always requiring both. I've also added a small hint for users running into this error when upgrading from earlier versions.

We will not consider this a breaking SDK change, as it doesn't change any protocols, but it will be a breaking CLI change.

- relates to #317 
- closes #256
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.

Detach GitHub path generation from name of the plugin

3 participants