Skip to content

PMM-4379 Add stubs for updates API. - #395

Merged
AlekSi merged 18 commits into
PMM-2.0from
PMM-4379-update-api-stubs
Jul 30, 2019
Merged

AlekSi merged 18 commits into
PMM-2.0from
PMM-4379-update-api-stubs

Conversation

@AlekSi

@AlekSi AlekSi commented Jul 17, 2019 •

Copy link
Copy Markdown
Contributor

No description provided.

@AlekSi AlekSi self-assigned this Jul 17, 2019
@percona percona deleted a comment from JNKPercona Jul 26, 2019
@percona percona deleted a comment from JNKPercona Jul 26, 2019
@percona percona deleted a comment from JNKPercona Jul 26, 2019
@percona percona deleted a comment from JNKPercona Jul 26, 2019
@percona percona deleted a comment from JNKPercona Jul 26, 2019
@percona percona deleted a comment from JNKPercona Jul 26, 2019
@percona percona deleted a comment from JNKPercona Jul 26, 2019
@percona percona deleted a comment from JNKPercona Jul 26, 2019
@AlekSi AlekSi mentioned this pull request Jul 28, 2019
5 tasks done
@percona percona deleted a comment from JNKPercona Jul 29, 2019
@percona percona deleted a comment from JNKPercona Jul 29, 2019
@percona percona deleted a comment from JNKPercona Jul 29, 2019
@percona percona deleted a comment from JNKPercona Jul 29, 2019
@percona percona deleted a comment from JNKPercona Jul 29, 2019
@AlekSi
AlekSi marked this pull request as ready for review July 29, 2019 08:04
@AlekSi
AlekSi requested review from BupycHuk and idexter July 29, 2019 08:04
Comment thread version/version_info.go
// Package version provides helpers for working with versions and build info.
package version

/*

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This code "works", but I would prefer not to use it if we can. It will be apparent if we need it or not soon.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why? Let's remove this file instead of commenting then.

@AlekSi AlekSi Jul 30, 2019 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

After this PR is squashed and merged, this code will be garbage collected by git / GitHub. It will be much harder to recover.
But after sleeping on it tonight, I'm 90% sure we will not need it. I will keep just in case in the git history but will remove in a next commit.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

ok

Comment thread .gitignore
/.vscode/

/api/vendor/
/vendor/

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Could you give some additional info, why have you moved vendor to root project directory?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

vendor/ moved to root just because of Gopkg.toml / Gopkg.lock moved to root.
Gopkg moved to root to properly add dependencies for /utils/pdeathsig package. /api/Gopkg.toml can't see /utils/... packages.
As a side effect, it actually fixed a problem of "key dependencies" versions not being fixed in downstream projects. Thanks to that we can remove hacks in them.

@percona percona deleted a comment from JNKPercona Jul 30, 2019
@percona percona deleted a comment from JNKPercona Jul 30, 2019
@JNKPercona

Copy link
Copy Markdown
Collaborator

Comment thread api/serverpb/server.proto
message VersionResponse {
// Full PMM version.
// Managed describes pmm-managed build information.
message Managed {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is it possible to have different version of pmm-managed and pmm-server?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Yes, during update. This field describes version embedded into pmm-managed binary during the build. Other fields describe version from RPM.
But this field exists mostly to debug build problems – and we actually found several thanks to it.

Comment thread version/version_info.go
// Package version provides helpers for working with versions and build info.
package version

/*

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why? Let's remove this file instead of commenting then.

@AlekSi
AlekSi merged commit c864f08 into PMM-2.0 Jul 30, 2019
@AlekSi
AlekSi deleted the PMM-4379-update-api-stubs branch July 30, 2019 09:38
artemgavrilov added a commit that referenced this pull request Jun 17, 2022
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