Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Specify sequence number with ff deploy

Open
  • Is something wrong?
#229 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go
Domain
blockchain, cli

Research direction

Start at the ff deploy command and trace how the chaincode sequence number is currently obtained or passed through. Clarify whether the intended behavior is an explicit sequence option or automatic incrementing, then define tests for repeated local deploys and the selected behavior.

Written by the indexing model from the issue text.

Description

As a developer, I want to update easily my chaincode on my local instance of Firefly.
I can do the first deploy as intended, but obviousely later deploys must have a greater sequence number.
I understand that ff deploy is more intenteded for CI, but it would be a great feature for easier testing.

I have two suggestions:

  1. add a --sequence/-s parameter or an additional optional arg to ff deploy to specify the sequence number
  2. or automate the thing and make the sequence number auto-incremented (I've done this in bash by counting the commited chaincodes)

Thanks a lot

Dominant language
Go
Stars
66
Forks
64
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from hyperledger-firefly/cli

All issues in hyperledger-firefly/cli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.