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

feat/Add version node attribute #267

Merged
merged 2 commits into from
Aug 9, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,10 @@
# Changelog

## [Unreleased]
Copy link
Contributor

Choose a reason for hiding this comment

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

diff link would be nice


### Added
- Well-known `Version` node attribute (#267)

## [2.14.0] - 2022-09-23 - Anmado (안마도, 鞍馬島)

### Added
Expand Down Expand Up @@ -485,3 +490,4 @@ Bump major release
[2.13.0]: https://github.com/nspcc-dev/neofs-api/compare/v2.12.0...v2.13.0
[2.13.1]: https://github.com/nspcc-dev/neofs-api/compare/v2.13.0...v2.13.1
[2.14.0]: https://github.com/nspcc-dev/neofs-api/compare/v2.13.1...v2.14.0
[Unreleased]: https://github.com/nspcc-dev/neofs-api/compare/v2.14.0...master
2 changes: 2 additions & 0 deletions netmap/types.proto
Original file line number Diff line number Diff line change
Expand Up @@ -206,6 +206,8 @@ message NodeInfo {
// Node's preferred way for communications with external clients.
// Clients SHOULD use these addresses if possible.
// Must contain a comma-separated list of multi-addresses.
// * Version
// Node implementation's version in a free string form.
//
// For detailed description of each well-known attribute please see the
// corresponding section in NeoFS Technical Specification.
Expand Down
3 changes: 3 additions & 0 deletions proto-docs/container.md
Original file line number Diff line number Diff line change
Expand Up @@ -98,6 +98,9 @@ Statuses:
response immediately. After a new block is issued in sidechain, request is
verified by Inner Ring nodes. After one more block in sidechain, the container
is added into smart contract storage.
NOTE: a container deletion leads to the removal of every object in that
container, regardless of any restrictions on the object removal (e.g. lock/locked
object would be also removed).

Statuses:
- **OK** (0, SECTION_SUCCESS): \
Expand Down
2 changes: 2 additions & 0 deletions proto-docs/lock.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,8 @@ Lock objects protects a list of objects from being deleted. The lifetime of a
lock object is limited similar to regular objects in
`__NEOFS__EXPIRATION_EPOCH` attribute. Lock object MUST have expiration epoch.
It is impossible to delete a lock object via ObjectService.Delete RPC call.
Deleting a container containing lock/locked objects results in their removal
too, regardless of their expiration epochs.


| Field | Type | Label | Description |
Expand Down
2 changes: 2 additions & 0 deletions proto-docs/netmap.md
Original file line number Diff line number Diff line change
Expand Up @@ -448,6 +448,8 @@ explicitly set:
Node's preferred way for communications with external clients.
Clients SHOULD use these addresses if possible.
Must contain a comma-separated list of multi-addresses.
* Version
Node implementation's version in a free string form.

For detailed description of each well-known attribute please see the
corresponding section in NeoFS Technical Specification.
Expand Down
Loading