sfctl is the Azure Service Fabric command-line interface, a powerful utility for interacting with and managing Service Fabric clusters, applications, and services. It provides a comprehensive set of commands for development, deployment, and operational tasks. The library maintains an active release cadence, with updates often aligning with new Service Fabric runtime versions to ensure compatibility and leverage new features. The current version is 11.2.1.
pip install sfctlNo compatibility data collected yet for this library.
After installation, use `sfctl -h` to see available commands. The first step is typically to connect to a Service Fabric cluster using `sfctl cluster select`. For secure clusters, you'll need to provide certificate paths (PEM or cert/key pair) and potentially use `--no-verify` for self-signed certificates, though this is not recommended for production environments.
Always use a version of sfctl compatible with your Service Fabric cluster runtime. Refer to the official Service Fabric CLI documentation for the recommended compatibility matrix. Upgrade both sfctl and your cluster if encountering compatibility warnings.
For self-signed certificates, ensure the certificate is correctly installed in your operating system's trusted root store. For secure clusters, specify the correct `--pem` or `--cert` and `--key` arguments. Avoid `--no-verify` in production.
Increase the default timeout using the `--timeout` parameter for large application packages. Ensure the client certificate is correctly configured and accessible to sfctl. For large packages, consider using the `--show-progress` option.
Upgrade your Python environment to version 3.8 or higher. Use `pip install sfctl` with a compatible Python 3 interpreter.
Ensure `pip install sfctl` completed successfully. Verify Python's script directory (e.g., `~/.local/bin` on Linux/macOS, `Scripts` in Python install dir on Windows) is in your system's PATH environment variable. Reinstall `sfctl` if necessary.
Upgrade your Service Fabric cluster, downgrade `sfctl` using `pip install sfctl==<compatible-version>`, or upgrade `sfctl` using `pip install --upgrade sfctl` to match your cluster. Always consult the official compatibility documentation.
For non-production/testing, add `--no-verify` to your `sfctl cluster select` command (e.g., `sfctl cluster select --endpoint https://... --pem ./client.pem --no-verify`). For production, import the cluster's certificate into your client machine's trusted root certification authorities store, or ensure you are using correctly issued certificates.
Verify the cluster endpoint URL and port are correct. Ensure the cluster is running and accessible from your machine (check network connectivity and firewall rules). For local clusters, confirm `http://localhost:19080` is the correct endpoint.
Ensure your `sfctl cluster select` command correctly specifies the client certificate (e.g., `--pem ./client.pem` or `--cert ./client.crt --key ./client.key`) before attempting application upload. Verify the certificate is valid and has permissions to interact with the image store.