这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@gitferry
Copy link
Member

Closes #289. With this pr, the fpd start flow becomes the follows:

  • If --eots-pk is specified, start the specified fp instance. Otherwise,
  • if no fp records found from db, start the daemon and show logs asking for registration
  • if there's one fp record found from db, start the daemon with the fp
  • if there are multiple fp record found from db, fail the cmd execution asking for set of --eots-pk

Copy link
Member

@Lazar955 Lazar955 left a comment

Choose a reason for hiding this comment

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

Nice work!


printRespJSON(res)

fmt.Println("You finality provider is successfully created. Please restart your fpd.")
Copy link
Member

Choose a reason for hiding this comment

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

let's use cmd.Println

Copy link
Contributor

@samricotta samricotta left a comment

Choose a reason for hiding this comment

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

Awesome, happy to have this change for testing purposes too

@vitsalis
Copy link
Member

Should we also update the docs to specify the rules for the --eots-pk flag?

@gitferry gitferry force-pushed the gai/improve-fpd-start branch from 5f47e20 to f702472 Compare January 24, 2025 04:52
@gitferry gitferry force-pushed the gai/improve-fpd-start branch from 26aa279 to 325dcfc Compare January 27, 2025 08:26
@gitferry gitferry merged commit 1c678fd into main Jan 27, 2025
15 checks passed
@gitferry gitferry deleted the gai/improve-fpd-start branch January 27, 2025 09:41
gitferry added a commit that referenced this pull request Jan 27, 2025
Closes #289. With this pr, the `fpd start` flow becomes the follows:

- If --eots-pk is specified, start the specified fp instance. Otherwise,
- if no fp records found from db, start the daemon and show logs asking
for registration
- if there's one fp record found from db, start the daemon with the fp
- if there are multiple fp record found from db, fail the cmd execution
asking for set of --eots-pk
gitferry added a commit that referenced this pull request Jan 27, 2025
Closes #289. With this pr, the `fpd start` flow becomes the follows:

- If --eots-pk is specified, start the specified fp instance. Otherwise,
- if no fp records found from db, start the daemon and show logs asking
for registration
- if there's one fp record found from db, start the daemon with the fp
- if there are multiple fp record found from db, fail the cmd execution
asking for set of --eots-pk
gitferry added a commit that referenced this pull request Jan 27, 2025
Closes #289. With this pr, the `fpd start` flow becomes the follows:

- If --eots-pk is specified, start the specified fp instance. Otherwise,
- if no fp records found from db, start the daemon and show logs asking
for registration
- if there's one fp record found from db, start the daemon with the fp
- if there are multiple fp record found from db, fail the cmd execution
asking for set of --eots-pk
gitferry added a commit that referenced this pull request Jan 27, 2025
Closes #289. With this pr, the `fpd start` flow becomes the follows:

- If --eots-pk is specified, start the specified fp instance. Otherwise,
- if no fp records found from db, start the daemon and show logs asking
for registration
- if there's one fp record found from db, start the daemon with the fp
- if there are multiple fp record found from db, fail the cmd execution
asking for set of --eots-pk
gitferry added a commit that referenced this pull request Jan 27, 2025
Closes #289. With this pr, the `fpd start` flow becomes the follows:

- If --eots-pk is specified, start the specified fp instance. Otherwise,
- if no fp records found from db, start the daemon and show logs asking
for registration
- if there's one fp record found from db, start the daemon with the fp
- if there are multiple fp record found from db, fail the cmd execution
asking for set of --eots-pk
gitferry added a commit that referenced this pull request Jan 27, 2025
Closes #289. With this pr, the `fpd start` flow becomes the follows:

- If --eots-pk is specified, start the specified fp instance. Otherwise,
- if no fp records found from db, start the daemon and show logs asking
for registration
- if there's one fp record found from db, start the daemon with the fp
- if there are multiple fp record found from db, fail the cmd execution
asking for set of --eots-pk
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.

Improve fpd start

5 participants