How rohitti12/ciscoise-terraform-automation-azure-functions works
Project type and purpose
• This is an Azure Functions project written in Python, aimed at automating configuration of Cisco ISE (Identity Services Engine) nodes in an Azure environment.
• It consists of two distinct serverless functions:
• A Timer‐triggered function that polls the ISE primary node and initiates syncing.
• An HTTP‐triggered function that reads configuration parameters from Azure App Configuration and applies them to ISE nodes.
File structure
• Top‐level function folders:
• HttpTrigger1/ – contains __init__.py, function.json, and sample.dat for the HTTP entry point.
• TimerTrigger1/ – contains __init__.py, function.json, readme.md, and sample.dat for the timer entry point.
• Global configs:
• host.json – Azure Functions host configuration
• requirements.txt – Python dependencies
• Metadata:
• .funcignore, .gitignore, CODEOWNERS, LICENSE, .github/ISSUE_TEMPLATE – project governance and CI/CD templates
Key points from the README
• Timer function: polls ISE primary, on healthy status triggers the HTTP function, checks sync.
• HTTP function: retrieves key/value pairs from Azure AppConfig and executes the main configuration routine for Primary, Secondary, and PSN nodes.
Main components
a. Azure Functions Host – the serverless runtime
b. TimerTrigger1 Function – scheduled execution (CRON)
c. HttpTrigger1 Function – REST endpoint or function‐to‐function call
d. Azure App Configuration Service – holds keys & values
e. Cisco ISE Nodes (Primary, Secondary, PSN) – target systems to configure
f. (Optional) Azure Storage or Logging – if used for monitoring or state
Architectural patterns and principles
• Serverless micro‐functions: each function has a single responsibility.
• Configuration as code: store all parameters in Azure AppConfig.
• Event‐driven orchestration: timer event drives the workflow, HTTP invocation chains tasks.
• Idempotent operations: ensure repeated runs don’t cause unintended side effects on ISE nodes.
Relevant technologies, frameworks, and libraries
• Azure Functions Python runtime
• Azure Functions SDK (function.json triggers/bindings)
• requests or azure‐identity (in requirements.txt) for REST calls
• Azure App Configuration client library
Final advice
• Be explicit about each function’s trigger type and binding.
• Sequence: Timer → HTTP → Config fetch → ISE calls.