Merge branch 'main' into workflow_token_permissions

Author: EnriqueL8

doc-site/docs/reference/firefly_interface_format.md

@@ -98,7 +98,7 @@ For example, the Ethereum plugin always needs to know what Solidity type the fie
 
 ## Automated generation of FireFly Interfaces
 
-A convenience endpoint exists on the API to facilitate converting from native blockchain interface formats such as an Ethereum ABI to the FireFly Interface format. For details, please see the <a href="/swagger/#/Default%20Namespace/postGenerateContractInterface" data-proofer-ignore>API documentation for the contract interface generation endpoint</a>.
+A convenience endpoint exists on the API to facilitate converting from native blockchain interface formats such as an Ethereum ABI to the FireFly Interface format. For details, please see the <a href="../../swagger/#/Default%20Namespace/postGenerateContractInterface" data-proofer-ignore>API documentation for the contract interface generation endpoint</a>.
 
 For an example of using this endpoint with a specific Ethereum contract, please see the [Tutorial to Work with custom smart contracts](../tutorials/custom_contracts/index.md).
 

doc-site/docs/tutorials/broadcast_data.md

@@ -20,7 +20,7 @@ title: Broadcast data
 ## Additional info
 
 - Key Concepts: [Broadcast / shared data](../overview/multiparty/broadcast.md)
-- Swagger Reference: <a href="/swagger/#/Default%20Namespace/postNewMessageBroadcast" data-proofer-ignore>POST /api/v1/namespaces/{ns}/messages/broadcast</a>
+- Swagger Reference: <a href="../../swagger/#/Default%20Namespace/postNewMessageBroadcast" data-proofer-ignore>POST /api/v1/namespaces/{ns}/messages/broadcast</a>
 
 ## Example 1: Inline string data
 

doc-site/docs/tutorials/create_custom_identity.md

@@ -11,7 +11,7 @@ Out of the box, a FireFly Supernode contains both an `org` and a `node` identity
 ## Additional info
 
 - Reference: [Identities](../reference/identities.md)
-- Swagger: <a href="/swagger/#/Default%20Namespace/postNewIdentity" data-proofer-ignore>POST /api/v1/identities</a>
+- Swagger: <a href="../../swagger/#/Default%20Namespace/postNewIdentity" data-proofer-ignore>POST /api/v1/identities</a>
 
 ## Previous steps: Start your environment
 

doc-site/docs/tutorials/define_datatype.md

@@ -20,7 +20,7 @@ of datatypes, as is used to broadcast the data itself.
 ## Additional info
 
 - Key Concepts: [Broadcast / shared data](../overview/multiparty/broadcast.md)
-- Swagger: <a href="/swagger/#/Default%20Namespace/postNewDatatype" data-proofer-ignore>POST /api/v1/namespaces/{ns}/datatypes</a>
+- Swagger: <a href="../../swagger/#/Default%20Namespace/postNewDatatype" data-proofer-ignore>POST /api/v1/namespaces/{ns}/datatypes</a>
 
 ### Example 1: Broadcast new datatype
 

doc-site/docs/tutorials/private_send.md

@@ -37,7 +37,7 @@ title: Privately send data
 ## Additional info
 
 - Key Concepts: [Private data exchange](../overview/multiparty/data_exchange.md)
-- Swagger: <a href="/swagger/#/Default%20Namespace/postNewMessagePrivate" data-proofer-ignore>POST /api/v1/namespaces/{ns}/messages/private</a>
+- Swagger: <a href="../../swagger/#/Default%20Namespace/postNewMessagePrivate" data-proofer-ignore>POST /api/v1/namespaces/{ns}/messages/private</a>
 
 ## Example 1: Pinned private send of in-line string data
 

doc-site/docs/tutorials/query_messages.md

@@ -17,7 +17,7 @@ This builds on the APIs to query and filter messages, described below
 ## Additional info
 
 - Reference: [API Query Syntax](../reference/api_query_syntax.md)
-- Swagger: <a href="/swagger/#/Default%20Namespace/getMsgs" data-proofer-ignore>GET /api/v1/namespaces/{ns}/messages</a>
+- Swagger: <a href="../../swagger/#/Default%20Namespace/getMsgs" data-proofer-ignore>GET /api/v1/namespaces/{ns}/messages</a>
 
 ### Example 1: Query confirmed messages
 

internal/database/sqlcommon/provider_sqlitego_test.go

@@ -46,7 +46,7 @@ type sqliteGoTestProvider struct {
 	capabilities *database.Capabilities
 }
 
-// newTestProvider creates a real in-memory database provider for e2e testing
+// newSQLiteTestProvider creates a real in-memory database provider for e2e testing
 func newSQLiteTestProvider(t *testing.T) (*sqliteGoTestProvider, func()) {
 	conf := config.RootSection("unittest.db")
 	conf.AddKnownKey("url", "test")

internal/identity/identitymanager.go

@@ -201,7 +201,7 @@ func (im *identityManager) ResolveInputVerifierRef(ctx context.Context, inputKey
 	}, nil
 }
 
-// ResolveInputIdentity takes in blockchain signing input information from an API call (which may
+// ResolveInputSigningIdentity takes in blockchain signing input information from an API call (which may
 // include author or key or both), and updates it with fully resolved and normalized values
 func (im *identityManager) ResolveInputSigningIdentity(ctx context.Context, signerRef *core.SignerRef) (err error) {
 	log.L(ctx).Debugf("Resolving identity input: key='%s' author='%s'", signerRef.Key, signerRef.Author)

internal/txcommon/txcommon.go

@@ -146,7 +146,7 @@ func (t *transactionHelper) SubmitNewTransaction(ctx context.Context, txType cor
 	return tx.ID, nil
 }
 
-// SubmitTransactionBatch is called to do a batch insertion of a set of transactions, and returns an array of the transaction
+// SubmitNewTransactionBatch is called to do a batch insertion of a set of transactions, and returns an array of the transaction
 // result. Each is either a transaction, or an idempotency failure. The overall action fails for DB errors other than idempotency.
 func (t *transactionHelper) SubmitNewTransactionBatch(ctx context.Context, namespace string, batch []*BatchedTransactionInsert) error {